Hi @GauravD2t : I gave this another look/test today. It's working, but some of the prior feedback has still not been addressed and tests are failing. Overall, this is looking much better and seems nearly ready... we just need to have an option to disable it.

1. In his review, @artlowel noted that we should provide an option to disable this feature as not all sites will want these facets on the homepage. I had also mentioned that in the original design discussion in this comment on the original ticket. I've copied my comment below:
   • "I also want to note that there are potential performance concerns with putting too much content on the homepage. At the very least, this feature needs to be possible to disable if it exists on the homepage."
   • To fix this issue, I'd recommend adding a new config similar to this:

     # This section already exists in `config.example.yml`
     homePage:
       # Enable or disable the Discover filters on the homepage
       showDiscoverFilters: true/false
     

2. Minor issue: I've noted the lines below where tests are failing and how to fix them.
3. Minor issue: There's a misalignment of code issue that I noted previously in search-filter.component.html. It looks like you can simply undo all changes to that file...as the only changes are to accidentally misalign the code (making the code harder to read)

Overall, this is looking good & I thank you for your hard work here.

@GauravD2t : Thanks for your hard work on this! I'm nearly a +1 as I can verify this is working properly. However, currently our automatic accessibility tests are failing on the homepage because the "Discover" header is an <h3> when it expects an <h2> (as there's no <h2> heading above that <h3>). I think we should try to find a way to fix this within this PR if possible. (If somehow this is too difficult, we could also consider temporarily disabling the failing accessibility test -- but I'm hopeful we won't need to do that.)

More information on the accessibility error inline below.

Thanks @GauravD2t

The new configuration option works for me, but I would still disable the feature by default. I'm not a fan of how it makes the homepage take up the full width of the window either

@GauravD2t : Thanks for the updates. I've given this a test today & all my prior feedback has been addressed. I think the final step is to disable this by default (as @artlowel requested above). I've added some notes inline on where those minor changes are necessary.

After these changes are made, I'll give it a final look & then squash merge it (so that it goes in as one commit instead of 70+). Thanks!

👍 Thanks @GauravD2t ! This all looks good to me now. Merging.